Shareware Grab Bag

home *** CD-ROM | disk | FTP | other *** search

/ Shareware Grab Bag / Shareware Grab Bag.iso / 001 / gtlog47.arc / GTLOG.DOC next >

Wrap

Text File | 1986-11-16 | 43.7 KB | 811 lines

GTLOG - An aid to GT Power Comm Release 4.6 16 November 1986 by James Davis GTLOG is a utility that was written to satisfy certain business needs and to make available a convenient way to track file movements, telephone usage, and telephone expenses. It was placed into the public domain, (ie, it was made available to anyone to use or copy without restrictions), for two reasons: 1) It proved to be very helpful to the author and, in short order, it made the author dependent upon the continued availability, usage, and support of GT Power Comm. No other vehicle, in the author's opinion, could be quite so compelling in terms of arguing for the continuity of GT Power Comm, than an exhibition of user support of this kind to the author of GT Power Comm (P & M Software Co. of Houston, Texas). Except, of course, your financial support to that author in the form of an earned and fair contribution to him. 2) It has been requested by other users of GT Power Comm and the author believes wholeheartedly in the concept of Shareware. No charge or contribution was requested for usage of this utility because it is not a stand-alone product. That is, it is merely a utility that works exclusively in conjunction with GT Power Comm. What does it do? o Creates reports from the log file that is created and maintained by GT Power Comm. (GT.LOG) o Provides file maintenance capabilities for the log file and for two additional files; a history file and a telephone rate table. (GTLOG.SUM and GTTELCO.EXP) o Allows the user to create these reports from any directory. o Outputs reports to display unit, printer, or disk file. James R. Davis 2010 Woodland Springs Houston, Texas 77077 (713) 558-5015 (voice) Table of Contents Release history .................. 3 What reports are available? ...... 4 How do I use the program? ........ 5 What happens when my Log becomes too large for convenience? ........... 5 Is there a recommended time to save my Log file? ..................... 5 What happens if I accidently lose my Log? ............................. 6 What can I do with these reports? 6 What files are used? ............. 6 Sample reports: File Summary report .............. 7 Uploads and performance .......... 8 Uploads by Files ................. 9 Uploads by Destination .......... 10 Downloads and performance ....... 11 Downloads by Files .............. 12 Downloads by Source ............. 13 Telephone Usage Detail .......... 14 Telephone Expense *ESTIMATES* ... 16 Bad Passwords ................... 17 U/L Descriptions ................ 18 Messages ........................ 19 Release history beginning with 4.6 Page 3 o Bug fix: Logs of size greater than 65,536 bytes may now be used. o Invalid log records are excluded from inclusion in History file. Release 4.5 o Bug fix: when new log was created the header was improperly setup. Release 4.4 o Bug correction: attempt to erase log and create a new one would yield an error message. Worse, it would erase both the existing log and the history file. These have been corrected. o The File Summary Report no longer shows entries where no file transfer activity has transpired. Release 4.3 o Modest cleanup of clear screen code. Release 4.2 o All beta testing has been completed with this release and it is scheduled to be the companion to GT PowerComm release 10.0 as of this date. No future functional releases are expected unless GT PowerComm adds new record types to the Log. o A major bug introduced in release 4.1 has been corrected. As release 4.1 was an internal beta test release, it affected no user's log. o File transfers that included sub-directory names are now handled properly. o Log entries that contained simply '??' for file size are now handled properly. o Manual dial entries usually contained no '-' delimiters and were, thus, recording improperly for telephone usage purposes and expense estimations. They are now properly handled. Release 4.1 Page 3a o Reports sent to disk are now ended with an EOF mark. o The user may now selectively purge just Messages from the Log or just U/L Descriptions. Making these selections will purge all irregularities from the log just as it does when clean-up is selected in addition to the selected record types. o All clean-up options now require user confirmation before the Log file is modified in any way. o Extra pages are no longer ejected from the printer between reports. o The correct Log Start date is now printed on Messages and U/L Descriptions reports. o Upload/Download reports by Destination/Source are no longer prematurely terminated if the user specifies a filename mask during a preceeding Upload/Download by Filename report. Release 4.0 Page 3b o This release includes code to detect and format the U/L DESC: records that are found in the log after receiving a file when in Host mode. Any description that would print beyond the end of the page is wrapped and right justified on the next line during a display or print of the entire Log. o In the event that GTPATH is found in the environment, and it does not begin with a drive specifier, GTLOG will now assume that the GT PowerComm files are on drive C:. It will, in any event, use the directory name specified in the environment. o Clean-up now properly eliminates zero length file transfers. o Clean-up now recognizes a zero length transfer regardless of the release level under which the log was written. o Clean-up may be aborted with an ESCape before executing it. o The user is not asked if history is wanted unless a history file exists. o The MSG: log entry is now recognized and support is provided in exactly the same form as it is for U/L Descriptions. o A report has been included that will format and display or print Messages or U/L Descriptions along with related info. o Clean-up will delete all messages, all U/L descriptions, and all invalid Host mode answer attempts from the log when run. o Messages and U/L descriptions do not get saved in the history file, nor do; passwords, bad passwords, and caller names from host mode sessions. Release 3.9 Page 3c o This is a major rewrite of the clean-up and save history code resulting from the requirement to be able to differentiate between CONNECTs and ANSWERs. o The Telephone Expense report no longer includes either Forced Carrier (Port-to-Port) or Host mode entries as these cannot result in telephone expenses. o Substantially enhanced ability of the program now exists to reconstruct a Log file from history. o The Log file clean-up function now creates PASSWORD records in the event that an ANSWER record appears with a PWD: field. Release 3.8 Page 3d o The password presented by a caller while in host mode is now shown in place of the dial string. o Should BAD PASSWORDs be detected without a corresponding ANSWER entry in the Log, the clean-up function will create such an entry. Release 3.7 Page 3e o Two new entries may now appear in the log as a result of using the Host mode feature of GT Power Comm. These include ANSWER and BAD PASSWORD which represent a successful connect during Host mode (meaning a valid password was specified) and an invalid password was specified, respectively. Both of these entries are now handled properly by GTLOG. The BAD PASSWORD entries may now be listed in a separate report. o The Log file clean-up function has been enhanced modestly and a minor bug was corrected as well. Release 3.6 Page 3f o The 'unformatted' display or print of the entire log file has had a bit more formatting added to it in order to make it a little easier to find related transactions. o The log file clean-up function now creates DISCONNECT entries to follow valid CONNECTs that were not normally disconnected. For such records that are created, the elapsed time of the connection will be shown as: '?:??.?? **Forced**'. Release 3.5 Page 3g o Users have been able to invoke GTLOG from a sub-directory other than the one in which the GT files are located for some time. Now they may also invoke the program from a different drive as well. Upon exit, GTLOG returns you to the drive and sub-directory you started from. o GT Power Comm may be used to transfer files between computers without the use of modems. This is known as a 'Port-to-Port' transfer and requires that GT Power Comm be set up with a Forced Carrier (via Alt-I). In such an environment GT Power Comm is not required to establish the connection via a dialing string and, therefore, it does not log either the CONNECT or the DISCONNECT within its Log. All file transfers, however, are properly recorded in its log. GTLOG has been enhanced with this release such that it recognizes when a file transfer record exists in the Log that is not preceeded by a CONNECT record and it can create such a record for you. Obviously, it will also create the corresponding DISCONNECT record. Of particular note is the fact that GTLOG calculates the baud rate at which the file transfer occurred and, thus, it is able to provide all the performance information in the form of reports that have always been available for modem to modem file transfers. In order to add these new records to your Log (the CONNECTs and DISCONNECTs), the user should request option 7 from the Main Menu (File Maintenance of the Log file), then select option 3 from the sub-menu (Clean-up the Log file). Once this has been performed the Log will contain the new records and any reports that are requested will include the Port-to- Port file transfers. The BBS name will be: Carrier Forced - Port to Port o Any report that is limited to a single month of data will be titled: 'Log Subset:' followed by the name of the month. o Any records found in the history file (if it exists) that were written prior to release 3.0 will show up on reports with question marks appearing where information could not be found (ie, ?:??.?? for transfer time). Also, if it can not be determined whether that record was an Upload or a Download it will appear on both sets of reports. If you have never created a history file before, you will never see these question marks on your reports. o The Telephone Expense report now shows estimated expenses by time rate as well as totals. Additionally, it reports the average cost (estimate) per minute by time rate and for total billable calls. What reports? Page 4 o A complete, unformatted, listing of the log file. Actually, there is a modest amount of formatting involved. That is, reports are not allowed to print across page boundaries, lines longer than 80 characters are split across two output lines, and 'More' like control of displayed output is provided. o Performance report for either Uploads or Downloads which includes an analysis of transfer rates and efficiency. o File transfer report for either Uploads or Downloads, by Destination or Source, respectively. These reports may be further tailored to include only selected file names using a mask (including 'wildcard' specification). o Destination or Source report, by filename. o BBS File Summary report that includes both Upload and Download information, performance data, number of connects and earliest and latest connect dates. o Telephone Usage report which provides either Detailed or Summary information, by telephone number, of the number of connections, duration of calls (by standard rate zones), and totals. o Telephone Expense report that includes detailed information as to time and date of connects, durations (by standard rate zones), ESTIMATED expense of calls, and totals. Note that this report may be further qualified by the user to include 1) all calls found in the log, 2) only those calls that have a specified expense rate, or 3) only those calls to a specified telephone number. o An expense rate estimation report that includes as many as three monthly 'fixed' expenses plus an unlimited number of specified telephone numbers and corresponding rate estimates. Rate estimates are by standard telephone rate zones and include an estimate of the cost for the first minute and for each additional minute or partial minute. o Bad Passwords, U/L Descriptions and Messages in Log reports. o All reports may optionally include just the information found in the current log file or they may also include all the information found in the history file as well as the current log. o All reports, other than the history summary, may be further limited to include data from only a specified month. How do I use it? Page 5 The program is completely interactive and menu driven. To start the program merely type: GTLOG (presuming, of course, that the program is either in your default directory or can be found within the DOS 'path'. If you are running the program from a directory other than that which contains the log file, GTLOG will search through your system's environment looking for 'GTPATH=' which, if found, tells GT Power Comm where it's directory file is located. GTLOG will accept the entry from the environment whether it ends with a '\' or not. If no such entry is found, GTLOG will then look within the default directory for a file called 'GT.LOG'. If it finds that file then operation proceeds normally; if not, GTLOG will create a null log file in your default directory. Once the log file is found (or created), GTLOG will ask what your output device is to be. You may specify your display, the standard printer device, or a disk file. If you specify a disk file, GTLOG will request the file's name and if the file already exists it will give you the opportunity to abort or to write over it. Next, you will be asked to select the report that you desire. Certain selections will result in additional prompts which, hopefully, are self explanatory. At any time that you wish to abort the current function you may enter an ESCape character and the program will exit. Most menus also allow you to enter a '0' to mean a graceful exit to the prior function. Almost all prompts provide a default which is shown enclosed in brackets '[..]'. If you simply press the return key it will be assumed that you agree with the default provided. What happens when my log file becomes larger than I want it to be? At any time you may elect to erase the current log or to save the summary and usage information from it into a history file before erasing. When you save information from the log that data is appended to the existing history file (or a new file is created if none exists at the time) so that no history is ever lost. While the history file is substantially smaller than the source log file, it is not maintained in a compacted format. This results in a much improved performance when preparing subsequent reports that include history information. Is there a recommended time to save the current log into history? Yes. It makes a lot of sense to save the current log into history at the end of every month. In that way you may always prepare a current month's set of reports and, should the need arise to include history, you can always include history data. What happens if I lose my log file or I have erased it and Page 6 want to restore from the history file? GTLOG provides the ability to do just that. It will extract information from the history file and literally create entries in your log in essentially the same format as the original log was created. Further, if you have not lost, erased, or 'trashed' your log, you may append the current log to the one that is created from your history file. That is, GTLOG allows you to replace your log (if it exists or not) by creating a new one from your history file, or, it will allow you to preface your existing log with the contents of the history file. NOTE, when you do either of these things the history file will be erased!! This is to prevent you from creating duplicate entries when you next save your log into history. What can I do with these reports? (After all, why does this program exist, if it has no practical value?) With the reports from this program you can answer questions like: o Where did I get this file from, and when? o Where have I sent this file to, and when? o Which BBS's are the most efficient? (ie, fastest) o How many times have I called a particular BBS and when was the last time? o How much time have I spent on a particular BBS this month? o What are my computer related telephone expenses going to be this month? o What are my calling patterns, in terms of when do I initiate my calls? (ie, is there a better pattern that will reduce my costs?) *** o What should I bill my client for the telephone charges I've incurred to support him? The last of these questions is the reason that I wrote this utility in the first place. As a consultant, I am reimbursed for such expenses and my clients prefer to get some documentation supporting my charges. What files are used? GT.LOG : PowerComm log GTLOG35.EXE : Log analyzer program GTLOG.SUM : Log history GTLOG35.DOC : This document GTTELCO.EXP : Telephone rate table BBS File Summary report ** SAMPLE ** Page 7 LOG STARTED: 9-10-86 as of 9/16/86 at 12:04 - BBS File Summary report =============================================================================== : Uploads Avg: Downloads Avg: Connects BBS Name : # Size CPS: # Size CPS: First Last # =============================================================================== Anything Goes ................: 1 69.69k 101: 0 ............: 9-10 9-11 1 Artichoke ....................: 1 74.64k 204: 0 ............: 9-15 9-15 1 Big Boys .....................: 0 ............: 0 ............: 9-12 9-12 2 COMPUTECH ....................: 1 70.23k 195: 2 117.00k 218: 9-12 9-12 1 Carrier Forced - Port to Port : 1 6.00k 410: 6 36.00k 180: 9-14 9-16 7 Fido's Partner ...............: 1 74.64k 182: 0 ............: 9-15 9-15 1 Jack Tejada ..................: 0 ............: 1 2.25k 92: 9-15 9-15 1 Mother Board (P. Headcrash) ..: 0 ............: 0 ............: 9-11 9-11 1 PC Interconnection ...........: 1 74.64k 181: 0 ............: 9-15 9-15 1 PC-Colt ......................: 0 ............: 0 ............: 9-15 9-15 1 Programmer's Workshop (10pm) .: 2 144.33k 203: 1 7.50k 192: 9-10 9-15 3 SCS Hotline ..................: 1 70.95k 106: 0 ............: 9-15 9-15 1 TBL-COMM .....................: 1 74.64k 204: 0 ............: 9-15 9-15 1 Tri-BBS ......................: 1 74.64k 204: 0 ............: 9-15 9-15 1 Trucraft .....................: 1 8.57k 101: 0 ............: 9-15 9-15 1 Zachary*Net ..................: 1 74.64k 185: 0 ............: 9-15 9-15 1 === ======== === === ======== === === 13 817.61k 180 10 162.75k 207 25 Uploads and performance report ** SAMPLE ** Page 8 LOG STARTED: 9-10-86 as of 9/16/86 at 12:05 - Uploads and performance =============================================================================== :Filename : Bytes : Time :Destination Blks/M : Eff % =============================================================================== X24:GTLOG30.ARC 69.69k 0:05.52 Programmer's Workshop (10pm) . 95.03 84.47% X12:GTLOG30.ARC 69.69k 0:11.44 Anything Goes ................ 47.51 84.47% X24:GTLOG31.ARC 70.23k 0:06.08 COMPUTECH .................... 91.61 81.43% X24:GTLOG32.ARC 74.64k 0:07.03 PC Interconnection ........... 84.70 75.28% X24:GTLOG32.ARC 74.64k 0:06.17 Programmer's Workshop (10pm) . 95.03 84.47% X24:GTLOG32.ARC 74.64k 0:06.53 Zachary*Net .................. 86.75 77.11% X24:GTLOG32.ARC 74.64k 0:06.15 Artichoke .................... 95.54 84.92% X24:GTLOG32.ARC 74.64k 0:07.00 Fido's Partner ............... 85.30 75.82% X24:GTLOG32.ARC 74.64k 0:06.14 TBL-COMM ..................... 95.79 85.15% X24:GTLOG32.ARC 74.64k 0:06.15 Tri-BBS ...................... 95.54 84.92% X12:LISTBI.ARC 8.57k 0:01.27 Trucraft ..................... 47.31 84.10% X12:GTLOG33.ARC 70.95k 0:11.23 SCS Hotline .................. 49.86 88.65% X96:LISTBI.ZBA 6.00k 0:00.15 Carrier Forced - Port to Port 192.00 42.67% =============================================================================== 13 Files 817.60k 1:22.46 H:M.S Overall average = 84.55 82.10% =============================================================================== .3% of time 6.00k 0:00.15 H:M.S @ 9600 baud average =192.00 42.67% 70.0% of time 662.38k 0:57.57 H:M.S @ 2400 baud average = 91.67 81.49% 29.7% of time 149.21k 0:24.34 H:M.S @ 1200 baud average = 48.62 86.44% Uploads by Files report ** SAMPLE ** Page 9 LOG STARTED: 9-10-86 as of 9/16/86 at 12:05 - Uploads by Files:????????.??? =============================================================================== Filename : Destination : Protocol Speed Date Time =============================================================================== GTLOG30.ARC : Anything Goes ................ : X 1200 9-11 0:13 : Programmer's Workshop (10pm) . : X 2400 9-10 23:49 GTLOG31.ARC : COMPUTECH .................... : X 2400 9-12 8:29 GTLOG32.ARC : Artichoke .................... : X 2400 9-15 1:46 : Fido's Partner ............... : X 2400 9-15 2:03 : PC Interconnection ........... : X 2400 9-15 0:42 : Programmer's Workshop (10pm) . : X 2400 9-15 0:58 : TBL-COMM ..................... : X 2400 9-15 2:19 : Tri-BBS ...................... : X 2400 9-15 2:34 : Zachary*Net .................. : X 2400 9-15 1:16 GTLOG33.ARC : SCS Hotline .................. : X 1200 9-15 16:44 LISTBI.ARC : Trucraft ..................... : X 1200 9-15 15:29 LISTBI.ZBA : Carrier Forced - Port to Port : X 9600 9-16 8:38 Uploads by Destination report ** SAMPLE ** Page 10 LOG STARTED: 9-10-86 as of 9/16/86 at 12:05 - Uploads by Destination =============================================================================== Destination : File name : Size : Baud CPS : Date Time =============================================================================== Anything Goes ................ : GTLOG30.ARC : 69k : 1200 101.4 : 9-11 0:13 ====== ===== 69k 101.4 Artichoke .................... : GTLOG32.ARC : 74k : 2400 203.8 : 9-15 1:46 ====== ===== 74k 203.8 COMPUTECH .................... : GTLOG31.ARC : 70k : 2400 195.4 : 9-12 8:29 ====== ===== 70k 195.4 Carrier Forced - Port to Port : LISTBI.ZBA : 6k : 9600 409.6 : 9-16 8:38 ====== ===== 6k 409.6 Fido's Partner ............... : GTLOG32.ARC : 74k : 2400 182.0 : 9-15 2:03 ====== ===== 74k 182.0 PC Interconnection ........... : GTLOG32.ARC : 74k : 2400 180.7 : 9-15 0:42 ====== ===== 74k 180.7 Programmer's Workshop (10pm) . : GTLOG30.ARC : 69k : 2400 202.7 : 9-10 23:49 : GTLOG32.ARC : 74k : 2400 202.7 : 9-15 0:58 ====== ===== 143k 202.7 SCS Hotline .................. : GTLOG33.ARC : 70k : 1200 106.4 : 9-15 16:44 ====== ===== 70k 106.4 TBL-COMM ..................... : GTLOG32.ARC : 74k : 2400 204.4 : 9-15 2:19 ====== ===== 74k 204.4 Tri-BBS ...................... : GTLOG32.ARC : 74k : 2400 203.8 : 9-15 2:34 ====== ===== 74k 203.8 Trucraft ..................... : LISTBI.ARC : 8k : 1200 100.9 : 9-15 15:29 ====== ===== 8k 100.9 Zachary*Net .................. : GTLOG32.ARC : 74k : 2400 185.1 : 9-15 1:16 ====== ===== 74k 185.1 Downloads and performance report ** SAMPLE ** Page 11 LOG STARTED: 9-10-86 as of 9/16/86 at 12:05 - Downloads and performance =============================================================================== :Filename : Bytes : Time :Source Blks/M : Eff % =============================================================================== Y24:QMDM22DK.ARC 44.00k 0:03.27 COMPUTECH ....................102.03 90.69% Y24:QM22-SUP.ARC 73.00k 0:05.42 COMPUTECH ....................102.46 91.07% X96:LISTBI.ZBA 6.00k 0:00.21 Carrier Forced - Port to Port 137.14 30.48% X24:PCBOARD.ARC 7.50k 0:00.40 Programmer's Workshop (10pm) . 90.00 80.00% X12:ATNIP.PRN 2.25k 0:00.25 Jack Tejada .................. 43.20 76.80% X48:LISTBI.ZBA 6.00k 0:00.27 Carrier Forced - Port to Port 106.67 47.41% X24:LISTBI.ZBA 6.00k 0:00.41 Carrier Forced - Port to Port 70.24 62.44% X12:LISTBI.ZBA 6.00k 0:01.08 Carrier Forced - Port to Port 42.35 75.29% X 3:LISTBI.ZBA 6.00k 0:03.47 Carrier Forced - Port to Port 12.69 90.22% X96:LISTBI.ZBA 6.00k 0:00.21 Carrier Forced - Port to Port 137.14 30.48% =============================================================================== 10 Files 162.75k 0:16.59 H:M.S Overall average = 96.95 82.51% =============================================================================== 4.1% of time 12.00k 0:00.42 H:M.S @ 9600 baud average =137.14 30.48% 2.6% of time 6.00k 0:00.27 H:M.S @ 4800 baud average =106.67 47.41% 61.8% of time 130.50k 0:10.30 H:M.S @ 2400 baud average =100.12 88.99% 9.1% of time 8.25k 0:01.33 H:M.S @ 1200 baud average = 42.58 75.70% 22.3% of time 6.00k 0:03.47 H:M.S @ 300 baud average = 12.69 90.22% Downloads by Files report ** SAMPLE ** Page 12 LOG STARTED: 9-10-86 as of 9/16/86 at 12:05 - Downloads by Files:????????.??? =============================================================================== Filename : Source : Protocol Speed Date Time =============================================================================== ATNIP.PRN : Jack Tejada .................. : X 1200 9-15 14:02 LISTBI.ZBA : Carrier Forced - Port to Port : X 9600 9-14 23:05 : Carrier Forced - Port to Port : X 4800 9-16 8:28 : Carrier Forced - Port to Port : X 2400 9-16 8:30 : Carrier Forced - Port to Port : X 1200 9-16 8:31 : Carrier Forced - Port to Port : X 300 9-16 8:36 : Carrier Forced - Port to Port : X 9600 9-16 8:37 PCBOARD.ARC : Programmer's Workshop (10pm) . : X 2400 9-15 1:00 QM22-SUP.ARC : COMPUTECH .................... : Y 2400 9-12 8:43 QMDM22DK.ARC : COMPUTECH .................... : Y 2400 9-12 8:37 Downloads by Source report ** SAMPLE ** Page 13 LOG STARTED: 9-10-86 as of 9/16/86 at 12:05 - Downloads by Source =============================================================================== Source : File name : Size : Baud CPS : Date Time =============================================================================== COMPUTECH .................... : QM22-SUP.ARC : 73k : 2400 218.6 : 9-12 8:43 : QMDM22DK.ARC : 44k : 2400 217.7 : 9-12 8:37 ====== ===== 117k 218.2 Carrier Forced - Port to Port : LISTBI.ZBA : 6k : 9600 292.6 : 9-14 23:05 : LISTBI.ZBA : 6k : 4800 227.6 : 9-16 8:28 : LISTBI.ZBA : 6k : 2400 149.9 : 9-16 8:30 : LISTBI.ZBA : 6k : 1200 90.4 : 9-16 8:31 : LISTBI.ZBA : 6k : 300 27.1 : 9-16 8:36 : LISTBI.ZBA : 6k : 9600 292.6 : 9-16 8:37 ====== ===== 36k 180.0 Jack Tejada .................. : ATNIP.PRN : 2k : 1200 92.2 : 9-15 14:02 ====== ===== 2k 92.2 Programmer's Workshop (10pm) . : PCBOARD.ARC : 7k : 2400 192.0 : 9-15 1:00 ====== ===== 7k 192.0 Telephone Usage Detail report ** SAMPLE ** Page 14 LOG STARTED: 9-10-86 as of 9/16/86 at 12:05 - Telephone Usage Detail =============================================================================== Telephone number : Day : Date : Time| Daytime : Evening : Night/WE | Total =============================================================================== Force : Sun : 9-14:23:05| : : 0:00.21 | Force : Tue : 9-16: 8:28| 0:00.27 : : | Force : Tue : 9-16: 8:30| 0:00.41 : : | Force : Tue : 9-16: 8:31| 0:01.08 : : | Force : Tue : 9-16: 8:36| 0:03.47 : : | Force : Tue : 9-16: 8:37| 0:00.21 : : | Force : Tue : 9-16: 8:38| 0:00.15 : : | Carrier Forced - Port to Port : === | ======== : ======== : ======== | ======= : 7 | 0:06.39 : 0:00.00 : 0:00.21 0:06.60 324-3416 : Fri : 9-12: 8:13| 0:00.03 : : | 324-3416 : Fri : 9-12: 8:14| 0:00.03 : : | Big Boys ..................... : === | ======== : ======== : ======== | ======= : 2 | 0:00.06 : 0:00.00 : 0:00.00 0:00.06 388-1889 : Wed : 9-10:23:58| : : 0:19.54 | Anything Goes ................ : === | ======== : ======== : ======== | ======= : 1 | 0:00.00 : 0:00.00 : 0:19.54 0:19.54 451-1421 : Mon : 9-15: 2:23| : : 0:11.22 | Tri-BBS ...................... : === | ======== : ======== : ======== | ======= : 1 | 0:00.00 : 0:00.00 : 0:11.22 0:11.22 458-7410 : Mon : 9-15: 1:51| : : 0:12.46 | Fido's Partner ............... : === | ======== : ======== : ======== | ======= : 1 | 0:00.00 : 0:00.00 : 0:12.46 0:12.46 466-1525 : Fri : 9-12: 8:16| 0:27.37 : : | COMPUTECH .................... : === | ======== : ======== : ======== | ======= : 1 | 0:27.37 : 0:00.00 : 0:00.00 0:27.37 xxx-xxxx : Mon : 9-15:14:01| 0:01.38 : : | Jack Tejada .................. : === | ======== : ======== : ======== | ======= : 1 | 0:01.38 : 0:00.00 : 0:00.00 0:01.38 537-8356 : Mon : 9-15: 0:24| : : 0:02.29 | PC-Colt ...................... : === | ======== : ======== : ======== | ======= : 1 | 0:00.00 : 0:00.00 : 0:02.29 0:02.29 661-9040 : Mon : 9-15: 2:05| : : 0:18.11 | TBL-COMM ..................... : === | ======== : ======== : ======== | ======= : 1 | 0:00.00 : 0:00.00 : 0:18.11 0:18.11 694-3150 : Mon : 9-15:16:30| 0:15.40 : : | SCS Hotline .................. : === | ======== : ======== : ======== | ======= : 1 | 0:15.40 : 0:00.00 : 0:00.00 0:15.40 LOG STARTED: 9-10-86 as of 9/16/86 at 12:05 - Telephone Usage Detail =============================================================================== Telephone number : Day : Date : Time| Daytime : Evening : Night/WE | Total =============================================================================== 772-2090 : Wed : 9-10:23:41| : : 0:12.28 | 772-2090 : Fri : 9-12: 2:48| : : 0:08.04 | 772-2090 : Mon : 9-15: 0:47| : : 0:13.50 | Programmer's Workshop (10pm) . : === | ======== : ======== : ======== | ======= : 3 | 0:00.00 : 0:00.00 : 0:34.22 0:34.22 933-7353 : Mon : 9-15: 1:02| : : 0:28.24 | Zachary*Net .................. : === | ======== : ======== : ======== | ======= : 1 | 0:00.00 : 0:00.00 : 0:28.24 0:28.24 946-4610 : Thu : 9-11: 0:18| : : 0:07.17 | Mother Board (P. Headcrash) .. : === | ======== : ======== : ======== | ======= : 1 | 0:00.00 : 0:00.00 : 0:07.17 0:07.17 955-8120 : Mon : 9-15: 0:27| : : 0:19.06 | PC Interconnection ........... : === | ======== : ======== : ======== | ======= : 1 | 0:00.00 : 0:00.00 : 0:19.06 0:19.06 978-3554 : Mon : 9-15: 1:31| : : 0:18.46 | Artichoke .................... : === | ======== : ======== : ======== | ======= : 1 | 0:00.00 : 0:00.00 : 0:18.46 0:18.46 1-212-xxx-xxxx : Mon : 9-15:15:27| 0:12.02 : : | Trucraft ..................... : === | ======== : ======== : ======== | ======= : 1 | 0:12.02 : 0:00.00 : 0:00.00 0:12.02 =============================================================================== Totals = 25 | 1:03.42 : 0:00.00 : 2:52.58 | 3:56.40 =============================================================================== *********************************************** Daytime = 8:00 < 17:00 Evening = 17:00 < 23:00 Night = 23:00 < 08:00 (or Saturday or Sunday) *********************************************** Telephone Expense *ESTIMATES* report ** SAMPLE ** Page 16 LOG STARTED: 9-10-86 as of 9/16/86 at 12:06 - Telephone Expense *ESTIMATES* =============================================================================== Telephone number : Day : Date : Time| Daytime : Evening : Night/WE | Expense =============================================================================== 1-212-xxx-xxxx : Mon : 9-15:15:27| 0:12.02 : : | $4.72 Trucraft ..................... : === | ======== : ======== : ======== | ======= : 1 | 0:12.02 : 0:00.00 : 0:00.00 | $4.72 =============================================================================== Totals = 1 | 0:12.02 : 0:00.00 : 0:00.00 | 0:12.02 =============================================================================== Billable = 1 | 0:12.02 : 0:00.00 : 0:00.00 | 0:12.02 Estimate = | $4.72 : $.00 : $.00 | $4.72 Cost/Min = | $.39 : n/a : n/a | $.39 ******************************************************************************* Daytime = 8:00 < 17:00 Total Monthly fixed = $12.13 Evening = 17:00 < 23:00 Total ESTIMATED tolls = $4.72 Night = 23:00 < 08:00 (or Saturday or Sunday) ******************************************************************************* List of Bad Passwords report ** SAMPLE ** Page 17 LOG STARTED: 8-15-86 as of 9/23/86 at 20:41 - List of Bad Passwords in Log =============================================================================== 9-22 11:52 BAD PASSWORD: PRIVAT From: Attempt 9-22 11:52 BAD PASSWORD: PO From: Attempt List of Messages in Log ** SAMPLE ** Page 18 LOG STARTED: 8-15-86 as of 9/23/86 at 20:42 - List of Messages in Log =============================================================================== 9-22 23:30 From: Jim Heironimus *Test message. 9-22 23:32 From: Manual Dial *This is a test of the message function within GTLOG release 40. *This is the second of two messages List of U/L Descriptions in Log ** SAMPLE ** Page 19 LOG STARTED: 8-15-86 as of 9/23/86 at 20:42 - List of U/L Descriptions in Log =============================================================================== 9-22 11:59 File: HAYES24.ARC From: Jim Davis *This file describes all the parameters available to users of the Hayes 2400 *b modem. It is a complete quick reference card. 9-22 14:04 File: GTLOG40.ARC From: Jim Davis *v4.0 GT PowerComm Log analyzer